Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/fastembed/recipe.yaml, recipes/py-rust-stemmers/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/py-rust-stemmers/recipe.yaml:

• ❌ Non noarch packages should have python requirement without any version constraints.
• ❌ Non noarch packages should have python requirement without any version constraints.

For recipes/py-rust-stemmers/recipe.yaml:

• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13015439110. Examine the logs at this URL for more detail.}

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/py-rust-stemmers/recipe.yaml, recipes/fastembed/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/py-rust-stemmers/recipe.yaml:

• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13015467373. Examine the logs at this URL for more detail.}

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/py-rust-stemmers/recipe.yaml, recipes/fastembed/recipe.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/fastembed/recipe.yaml, recipes/py-rust-stemmers/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/fastembed/recipe.yaml:

• ❌ Non noarch packages should have python requirement without any version constraints.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13264816711. Examine the logs at this URL for more detail.}

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/py-rust-stemmers/recipe.yaml, recipes/fastembed/recipe.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13286206003. Examine the logs at this URL for more detail.}

we should be able to remove the <3.13 pin after conda-forge/mmh3-feedstock#25 is merged

depends on #29104

@conda-forge/help-python, ready for review!

@wolfv the linter still doesn't seem to like the conditional syntax of v1 recipes, similar to here. Can we still merge this?

Ah yes, because it's a noarch package. What you are looking for is the conditional dependencies that we are currently proposing in a CEP.

For a noarch package, only a single repodata entry will be created that has to be valid for all Python versions.

There are a number of workarounds to this issue but they all involve creating additional packages.

ahh I see 🥲 why did it work for the nested syntax though? Did it just fill one of the versions and that worked although it wasn't a conditional specification anymore?

As a fix, can I just bump the min_python to a version that doesn't require the complex conditionals?

Yeah, only one of your combinations would have made it into the metadata.

You can totally restrict the Python version that works with your package.

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/fastembed/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/fastembed/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13289401845. Examine the logs at this URL for more detail.}

done! is this fine?